Cron job #898
Open
Cron job #898
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cron job is working now and containerized. it is added to the development yml so that it will start up with the other containers
prep branch for pull request by removing changes that are not necessary to the functionality of the cron job
when certain errors occur we make note of it rather than just crashing and ending our scrape
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
no database modifications
Test Procedure
the scraper runs at the beginning of every hour. you may wait for the cron job to start and then check "/var/log/cron.log" to see if it is working. It should print "Our test works at", <datetime.now()>)". If you do not want to wait, you can test to ensure that the python script works by running the following command in the docker container.
"/usr/local/bin/python3 /usr/src/no_login.py"
Note that this is not testing if cron is running the job automatically, but rather that the scraper is functioning as expected within the docker container.